-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BC-8551 - Delete const ALL_ENTITIES #5446
base: main
Are you sure you want to change the base?
Conversation
…sage place. -> Currently some parts should be broken.
…schul-cloud/schulcloud-server into BC-8551-remove-all-entities
apps/server/src/modules/deletion-console/deletion-execution.console.spec.ts
Show resolved
Hide resolved
import path from 'path'; | ||
import { ENTITIES } from './management.entity.imports'; | ||
|
||
const migrationsPath = path.resolve(__dirname, '..', '..', 'migrations', 'mikro-orm'); // TODO: Warum ist das hier überhaupt relevant? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// TODO: Import Reihenfolge sieht falsch aus ...IDM prüfen.
// TODO: Warum ist das hier überhaupt relevant?
Kann raus
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Imports schein richtig zu sein
Zeile 17 zeigt wo migrations Files liegen
import { createConfigModuleOptions } from '@shared/common/config-module-options'; | ||
import { ConsoleModule } from 'nestjs-console'; | ||
import path from 'path'; | ||
import { ENTITIES } from './management.entity.imports'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hier brauchen wir alle Entities. Z.B. auch fileRecord, sollten wir aktuell eine Migration schreiben, oder eine existierende ausführen. Daher die Überlegung mit dem regex.
…pdate database management console methods to public
import { FilesStorageClientModule } from '@infra/files-storage-client'; | ||
import { RabbitMQWrapperModule } from '@infra/rabbitmq'; | ||
import { MikroOrmModule } from '@mikro-orm/nestjs'; | ||
import { FilesStorageClientModule as FilesMetadataClientModule } from '@modules/files-storage-client'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hier sind beide file-storage-clients drin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ja 😭
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh neinnnnnn 😭
…d update deletion logic
…ge-client modules
apps/server/src/modules/deletion-console/deletion-console.app.module.ts
Outdated
Show resolved
Hide resolved
apps/server/src/modules/deletion-console/deletion-execution.console.spec.ts
Outdated
Show resolved
Hide resolved
apps/server/src/modules/files-storage-client/files-storage-client.module.ts
Outdated
Show resolved
Hide resolved
…rvice and update deletion logic" This reverts commit 3f8f5f8.
|
Description
Each app.module should import the entities they need directly. To make dependencies explicit. The linter rules must change in a way that allow the imports.
Links to Tickets or other pull requests
JIRA :
Deployments :
Approval for review
generate-client:server
was executed in vue frontend and changes were tested and put in a PR with the same branch name.